I am getting the following error when running the command on an SBS2K8 box and am now totally lost. I have an SRV record out at my domain for the autodiscover service. I think this may be related to the .local and .net but not 100% sure. Here is the error text: [PS] C:\Windows\system32>Test-OutlookWebServices | FL Id : 1003Type : InformationMessage : About to test AutoDiscover with the e-mail address Administrator@XXXssociates.net. Id : 1007Type : InformationMessage : Testing server XXXSSOCIATES01.XXXssociates.local with the published name https://sites/EWS/Exchange.asmx & . Id : 1019Type : InformationMessage : Found a valid AutoDiscover service connection point. The AutoDiscover URL on this object is https://remote.XXXssociates.local/autodiscove r/autodiscover.xml. Id : 1013Type : ErrorMessage : When contacting https://remote.XXXssociates.local/autodiscover/autod iscover.xml received the error The remote name could not be resolved: 'remote.sabassociates.local' Id : 1006Type : ErrorMessage : The Autodiscover service could not be contacted.

On Sat, 10 Apr 2010 20:02:02 +0000, scot43 wrote:>>>I am getting the following error when running the command on an SBS2K8 box and am now totally lost. I have an SRV record out at my domain for the autodiscover service. I think this may be related to the .local and .net but not 100% sure. Here is the error text: Can you run nslookup and resolve the name"remote.sabassociates.local"?If not, fix your DNS . . . or change the URL. FYI you won't be able touse that name from outside your organization because the .local TLDisn't usable beyond your own DNS.Depending on how you plan to use this (i.e. using just a single nameso your users won't want to strangle you) you'd probably want to run asplit DNS with the internal DNS resolving the name to an internal IPaddress and your external DNS resolvng the name to your96<dot>57<dot>220<dot>70 IP address.---Rich MatheisenMCSE+I, Exchange MVP--- Rich Matheisen MCSE+I, Exchange MVP

Rich, I am down to what i think is the last issue now. I am trying to correct the service discovery now. I do not have a "sites" certificate. Id : 1004Type : ErrorMessage : The certificate for the URL https://sites/EWS/Exchange.asmx is incorr ect. For SSL to work it needs to have a subject of sites, instead the subject was remote.sabassociates.net. Consider correcting service di scovery, or installing a correct SSL certificate.

On Mon, 12 Apr 2010 00:23:33 +0000, scot43 wrote:>I am down to what i think is the last issue now. I am trying to correct the service discovery now. I do not have a "sites" certificate. Why are you using a different server name for EWS? Shouldn't you beusing the remote.sabassociates.net name?> >>Id : 1004Type : ErrorMessage : The certificate for the URL https://sites/EWS/Exchange.asmx is incorr ect. For SSL to work it needs to have a subject of sites, instead the subject was remote.sabassociates.net. Consider correcting service di scovery, or installing a correct SSL certificate. ---Rich MatheisenMCSE+I, Exchange MVP--- Rich Matheisen MCSE+I, Exchange MVP

This was a migration install of SBS2k8 and I suspect that this is where the mischeif came from. I have made progress from this point. I am at the http/rpc as an issue and here is the printout: Id : 1013Type : ErrorMessage : When contacting https://remote.sabassociates.net/Rpc received the err or The server committed a protocol violation. Section=ResponseStatusL ine Id : 1017Type : ErrorMessage : [EXPR]-Error when contacting the RPC/HTTP service at https://remote.s abassociates.net/Rpc. The elapsed time was 31 milliseconds. Scott

Here is the printout from TESTEXCHANGECONNECTIVITY: Attempting to Ping RPC Proxy remote.sabassociates.net Cannot ping RPC Proxy Additional Details A Web Exception occurred because an HTTP 401 - Unauthorized response was received from Unknown

On Mon, 12 Apr 2010 11:13:10 +0000, scot43 wrote:>>>this is exactly where ant why I am confused, i need to check and change the EWS to look for the remote.sabassociates.net. This was a migration install of SBS2k8 and I suspect that this is where the mischeif came from. See the "Get-WebServicesVirtualDirectory", and"Set-WebServicesVirtualDirectory". You should be able to the URL easily enough.---Rich MatheisenMCSE+I, Exchange MVP--- Rich Matheisen MCSE+I, Exchange MVP

Hi, Please try to access https://localhost/rpc/rpcproxy.dll on the CAS, you should get the blank page. What's the result for you? Thanks Allen

Allen, I get a certificate warning and then the blank page. The certificate is "remote.sabassociates.net" as it should be. Do I need to correct it in another place?

Rich, I was able to correct that portion and am now at the http/rpc issue

Iam having the same messages when running the test-outlookWebServices cmdlet on my Exchange 2007 CAS server (also MBX and HT) Id : 1013 Type : Error Message : When contacting https://mail.mydomain.com/Rpc received the error The server committed a protocol violation. Section=ResponseStatusLine Id : 1017 Type : Error Message : [EXPR]-Error when contacting the RPC/HTTP service at https://mail. mydomain .com/Rpc. The elapsed time was 15 milliseconds. I am able to browse to https://mail.mydomain .com/rpc/rpcproxy.dll (blank page) after supplying credentials, both internally and externally. Outlook anywhere seems working fine as I am able to connect externally with outlook 2007. (tested creating new profiles using autodiscover) I also do not see problems when running the "Test e-mail Auto-configuration" from the PC w/outlook 2007 (both internally and externally) it is just on the CAS server when I run the test-outlookWebServices cmdlet. I have tried adding the server name in the hosts file in the CAS server, changing to Basic authentication instead of NTLM, disabling re-enabling outlook anywhere but the 1013 and 1017 messages keep showing. Any suggestions?

Hi Rich, That's normal behaviour. Now I would like like to confirm whether the Outlook Anywhere is working normally. Was the issue encountered only when testing test-outlookwebservices? Please try to use RPCPing command to test the connectivity of the RPC Proxy server based on the below command:rpcping -t ncacn_http -s ExchServer -o RpcProxy=RPCProxyServer -P "user,domain,*" -I "user,domain,*" -H 2 -u 10 -a connect -F 3 -v 3 -E -R nonehttp://support.microsoft.com/kb/831051 If that is working, I suspect this issue can be caused ASP.Net 2.0. I did more research on the error. The message "The server committed a protocol violation" actually is an error reported in ASP.Net 2.0. When command Test-OutlookWebServices performs the tests, requests are sent in HTTP (with TLS) and then IIS server replies. In case the HTTP response can't be correctly handled by the .Net code, the error will be returned. Based on my research, this issue only occurs when querying on local computer. Would you please try to running the command on other servers. In case the error only occurs on the CAS server itself, we can safely ignore it as other clients won't encounter this issue. Thanks Allen

Hi, Any update on this issue? Thanks Allen

i am still getting the issue running the test from a client machine. Additionally, all of a sudden 1 of my client machines that is on the local LAN started prompting for UN/PW for outlook with NO work having been done on the server.